Systems and methods for integrating storage resources from storage area network in machine provisioning platform

ABSTRACT

Embodiments relate to systems and methods for integrating storage resources from a storage area network in a machine provisioning platform. A provisioning platform can communicate generate and maintain a provisioning profile encoding the software, hardware, and/or other resources to be provisioned to a target physical and/or virtual machine. The provisioning profile can include a set of storage allocations for each target machine to be provisioned by the platform, indicating the high-level amounts, types, availability, so forth to be associated with each target. The provisioning profile can likewise include a set of storage specifications indicating specific disk types, manufacturers, and specific sources or pools in the set of storage resources available to the storage area network to transparently fulfill the storage allocations. The target(s) can be assigned an alias to identify them to the SAN, and the provisioning platform can mount the corresponding storage resources during the provisioning or updating process.

FIELD

The present teachings relate to systems and methods for integrating storage resources from a storage area network in a machine provisioning platform, and more particularly to platforms and techniques for incorporating and configuring storage hosted in a storage area network into a newly provisioned or updated machine.

BACKGROUND OF RELATED ART

Provisioning platforms exist which permit a systems administrator or other user to instantiate, configure, and provision software installations on physical and virtual machines. Available provisioning platforms can, for instance, allow an administrator to create a profile or template for the operating system, application set, security, and other resources of a group of target machines. The provisioning platform can then, for example, invoke local installation daemons or other logic to distribute the selected operating system code and other code and resources down to the target machine in a “bare metal” or initial physical installation, an update delivery, and/or to a virtual machine hosted in a cloud or other network.

In the case of storage configurations, existing provisioning platforms can register the physical storage attached to one or more target machines, and reflect the available hard disk, optical disk, and/or other resources with the provisioning server or other logic, to record the configurations of the deployed machines. In existing provisioning platforms, however, there is no mechanism to integrate storage from an independent storage area network (or SAN) into the configuration profile of a set of new or updated machines. Existing provisioning platforms likewise lack the ability to select, specify, or configure specific storage sources from a SAN that can be accessed or used to fulfill the storage specifications of a newly provisioned or updated machine being serviced by the provisioning server. It may be desirable to provide methods and systems for integrating storage resources from a storage area network in a provisioning platform, wherein interfaces to the storage resources of a SAN can be built into the configuration process for newly provisioned or updated machines.

DESCRIPTION OF DRAWINGS

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the present teachings and together with the description, serve to explain the principles of the present teachings. In the figures:

FIG. 1 illustrates an overall system in which systems and methods for integrating storage resources from a storage area network in a machine provisioning platform can be implemented, according to various embodiments;

FIG. 2 illustrates an overall system in which systems and methods for integrating storage resources from a storage area network in a machine provisioning platform can be implemented, according to various further embodiments;

FIG. 3 illustrates an exemplary hardware configuration of a provisioning platform which can be used in systems and methods for integrating storage resources from a storage area network in a machine provisioning platform, according to various embodiments; and

FIG. 4 illustrates overall processing that can be used in provisioning and storage allocation operations, according to various embodiments of the present teachings.

DESCRIPTION OF EMBODIMENTS

Embodiments of the present teachings relate to systems and methods for integrating storage resources from a storage area network in a machine provisioning platform. More particularly, embodiments relate to platforms and techniques which include a provisioning platform, communicating with set of target machines to prepare and configure those machines, for network operation. In embodiments, the set of target machines under provisioning control can be or include physical or hardware-implemented machines, virtual machines, and/or combinations of each. According to aspects, provisioning activity can take place using a set of templates or profiles which encode the set of operating system, application software, communications, security, storage, and/or other hardware, software, or other resources to be implemented or hosted in each of the target machines.

In embodiments, at the time of provisioning or updating the configuration of one or more target machines, the provisioning platform can also incorporate information that can be used to associate the target machine(s) with a storage area network (SAN). The SAN identification information can permit the configured target to identify, access and/or mount storage resources located in the SAN, as part of the original or updated configuration process for the machine. In embodiments, the SAN identification information can comprise a world wide port name, as well as an alias which defines the target machine(s) as a node in the SAN network fabric. The SAN identification information can also include addressing or other information that can be used to locate and configure each target machine at sync time when provisioning operations are initiated, or at later times downstream of the initial provisioning activity. According to embodiments, each target machine can thereby integrally incorporate an allocation of storage resources, such as hard disk, optical, backup, and/or other resources, directly in the provisioning profile or template for that machine or other node. In embodiments, that storage allocation can comprise a size, amount, type, availability, and/or other specification for the storage resources to be extracted or assigned to the target(s) from the SAN.

According to embodiments, in addition to the high level storage allocations registered to each target in the provisioning profile or template, a set of storage specifications for the storage hardware to be accessed or used to fulfill the high level allocations can also be built into the provisioning profile or template. In aspects, the set of storage specifications can comprise a set of lower level specifications or parameters that can be used to locate, access, and/or mount particular storage hardware, software, or other resources to fulfill the high level storage allocations. For instance, in embodiments, the set of storage specifications can comprise information regarding or identifying hard disk or optical disk size, speed, level of redundancy such as RAID (redundant array of inexpensive disk) backup level, storage availability, preferred hardware vendors, and/or other specifications or details for the storage hardware to be used according to a target machine's high level storage allocation.

According to embodiments, a systems administrator or other user can, for instance, update or change the set of storage specifications for a target machine or class of target machines, without necessarily changing or updating the set of high level storage allocations assigned to those machines. In aspects, specific storage hardware assets can be installed, updated, changed, or substituted, transparently to the users of the target machines, since the high level storage allocations can remain the same. These and other embodiments described herein address the various noted shortcomings in known provisioning platform technology, and provide a user or network operator with enhanced flexibility and power in the management of provisioning operations.

Reference will now be made in detail to exemplary embodiments of the present teachings, which are illustrated in the accompanying drawings. Where possible the same reference numbers will be used throughout the drawings to refer to the same or like parts.

FIG. 1 illustrates an overall network 300 in which systems and methods for integrating storage resources from a storage area network in a machine provisioning platform can operate, according to various embodiments. In embodiments, provisioning platform 302 can be or include provisioning platforms, hardware, software, and other resources such as those described in copending U.S. patent application Ser. No. 11/763,315, U.S. Pat. No. ______ and U.S. patent application Ser. No. 11/763,333, U.S. Pat. No. ______, each of which applications is assigned or under obligation of assignment to the same entity as this application, the disclosures of which applications are incorporated herein, in their entirety, by reference. In embodiments, provisioning platform 302 can comprise provisioning platforms, hardware, software, and other resources other than those described in the aforemention copending U.S. patent applications.

In embodiments as shown in FIG. 1, a systems administrator and/or other user can use or access provisioning platform 302 to set up, configure, monitor, and manage the provisioning of one or more machines in set of targets 306. In embodiments, provisioning platform 302 can host, access, and/or manipulate a provisioning profile 314 and/or other template to manage the provisioning, delivery, and/or configuration of software, hardware, and/or other resources to one or more machines or nodes in set of targets 306. In embodiments, set of targets 306 can comprise one or more servers, hosts, clients, targets, desktop computers, laptop computers, and/or other machines, nodes, or destinations. In embodiments, set of targets 306 can be or include network-enabled cellular telephones, network-enabled media playback devices, network-enabled gaming devices, and/or other devices, machines, and/or hardware. In embodiments, set of targets 306 can likewise or instead comprise one or more virtual machines. Virtual machines can comprise virtual machines instantiated under a virtual machine monitor and/or operating system configured to operate virtual machines and their associated resources. In embodiments, virtual machines in set of targets 306 can also or instead include cloud-based machines or resources.

According to embodiments, and as generally shown in FIG. 1, provisioning platform 302 can generate and store a set of storage allocations 322 for each machine in set of targets 306, indicating the high-level type, performance, and/or other parameters that will be assigned to a target. In embodiments, some or all of the set of storage allocations 322 can be fulfilled, hosted, implement, or otherwise realized using storage resources 310 of SAN 340, such as hard disks, optical disks, RAID arrays, solid state or electronic storage, and/or other storage resources. Set of storage allocations 322 can for instance comprise entries or fields for one, two, or more hard disks and/or optical disks, each with a given allocated size in gigabytes or other measures. Set of storage allocations 322 can likewise be or include entries or fields indicating that a target or other machine will be entitled to a certain amount, such as for instance 20 terabytes, of RAID storage or tape backup, and/or other backup resources or services. Other types, amounts, and configurations of storage can be encoded for a given machine in set of storage allocations 322. In embodiments, set of storage allocations 322 can be stored in provisioning profile 314 stored in provisioning store 312, but can, as illustrated, also or instead be stored in a target machine to which those resources are allocated. In embodiments, in addition to the comparatively high-level set of storage allocations 322, including storage amounts, provisioning platform 302 can also store set of storage specifications 324, which can likewise be stored in provisioning profile 314, in the target machine(s) themselves, and/or other data stores or destinations. In embodiments, set of storage specifications 324 can specify, for each target, group of targets, and/or other machines or nodes, the manufacturer, vendor, software compatibility specifications, and/or other comparatively low-level specifications of hardware present in SAN 340 from which SAN switch 308, provisioning platform 302, and/or other logic will provide the physical storage to fulfill set of storage allocations 322 for given target machine(s). In embodiments, set of storage specifications 324 can specify that for hard disk allocations, a given machine will be assigned one or more 500 gigabyte hard disks manufactured by X Corp., having a SCSI-III (small computer systems interface, version 3) interface rated at 10 megabytes/sec transfer rate on a 32 bit bus. Other specifications in set of storage specifications 324 are possible. In embodiments, provisioning platform 302 can assign, update, and/or change the assignments of physical resources in set of storage resources 310 used to satisfy the set of storage allocations 322 for one or more machines in set of targets 306. In embodiments, the assignment of particular storage resources via lookup in set et storage specifications 324 can be transparent to a user or provisioning platform 302, set of targets 306, and/or other resources.

More particularly, and as for instance shown in FIG. 2, provisioning platform 302 can host or store SAN identification information 320 for each machine, node, or host in set of targets 306, which identification information can locate or identify the machine configured to receive a set of storage allocations 322 from SAN 340. In embodiments, SAN identification information 320 can be or include a world wide port name (WWPN) identifier, which can act to identify one or more machines in set of targets 306 to SAN 340, including SAN switch 308 and/or other logic in the fabric of SAN 340. In embodiments, when provisioning platform 302 enters its sync phase in the execution of provisioning activity, and writes out a dhcp.conf (dynamic host control protocol.inf) file and/or initiates other provisioning activity, provisioning platform 302 can also log into SAN switch 308. Provisioning platform 302 can identify the WWPN or other SAN identification information 320 with a fiber channel alias or other identifier of the target machine(s). Provisioning platform 302 can also add the machine(s) being provisioned in set of targets 306 to any netgroups that are required to access defined storage under a network file system (NFS), and/or other network directory structure.

In embodiments, provisioning platform 302 can generate, access, update, and manage set of storage specifications 324 to fulfill the set of storage allocations 322 for a given target machine or machines. In embodiments, set of storage specifications can be stored into provisioning profile 314, and/or can be stored or registered to individual target machine(s) being provisioned. In embodiments, set of storage specifications 324 can comprise a record of a storage source, which can comprise one storage device or a pool of devices, and a destination mount associated with the provisioned machine(s). In embodiments, set of storage specifications 314 can contain an explicit reference to a storage source from within set of storage resources 310, in which case the storage can be generated and/or created on the target machine(s) or other host(s), with a directory path being specified. In embodiments, set of storage specifications 314 can store the identification of a storage pool in set of storage resources 310 rather than a discrete source, in which case provisioning platform 306 can select a device in the storage pool and instantiate or create the storage within that pool. In embodiments, the destination mount in the target machine(s) can be part of the kickstart process, such as the kickstart process described in the aforementioned U.S. patent application Ser. No. 11/763,315 and U.S. patent application Ser. No. 11/763,333, although it will again be understood that other provisioning platforms and provisioning processes can be used. When integrated into a kickstart or similar process, the destination mount can be made part of the kickstart process, and can be set up in provisioning profile 314 to cause the recipient target machine(s) to automatically format and mount that source, or source pool, at installation time. It may be noted that while network file system (NFS) and Fiber Channel implementations have been noted in connection with SAN 340, in embodiments, other file structures and connection fabric could be used. For instance, in embodiments, common Internet file system (CIFS) and/or iSCSI (Internet small computer system interface) file systems or connection channels can be used, as well as others.

FIG. 3 illustrates an exemplary configuration of a provisioning platform 302 which can be used in systems and methods for integrating storage resources from a storage area network in a machine provisioning platform, according to embodiments. In embodiments as shown, provisioning platform 302 can comprise a processor 330 communicating with memory 332, such as electronic random access memory, operating under control of or in conjunction with operating system 326. Operating system 326 can be, for example, a distribution of the Linux™ operating system, the Unix™ operating system, or other open-source or proprietary operating system or platform. Processor 330 also communicates with provisioning store 312, such as a local or remote database, which can be stored, for instance, on one or more hard drives, optical drives, magnetic drives, electronic memory, and/or other storage. Processor 330 further communicates with network interface 334, such as an Ethernet or wireless data connection, which in turn communicates with one or more network 304, such as the Internet or other public or private networks. Processor 330 can, for example, communicate with set of targets 306 via one or more network 304. Processor 330 can also communicate with a provisioning engine 338 which can comprise logic, hardware, and/or software resources for communicating with set of targets 306 and controlling provisioning activity on those machines and/or other nodes of managed network 304. Processor 330 can also communicate with SAN 340 including SAN switch 308, and/or and other resources to control the processing of provisioning and data storage allocation to set of targets 306, and/or other hosts, targets, machines, or nodes. Other configurations of provisioning platform 302, associated network connections, and other hardware and software resources are possible.

FIG. 4 illustrates a flowchart of data processing operations that can be used in systems and methods for integrating storage resources from a storage area network in a machine provisioning platform, according to various embodiments. In 402, processing can begin. In 404, a provisioning, updating, and/or other distribution process can be initiated, for instance via provisioning platform 302 and/or other logic or resources. In 406, set of storage allocations 322 for one or more targets or machines in set of targets 306 that are the intended recipients of the provisioning process can be received and/or accessed. In 408, SAN identification information 320 associated with one or more recipient target machines to identify those machines to the SAN 340 and other network resources can be generated and/or received. In aspects, SAN identification information 320 can be or include an alias and/or other information which locates or identifies the target machine(s) to the SAN 340, managed network 304, and/or other networks, connections, or resources. In embodiments, the alias can comprise a network address such as an Internet address, a subnet address, a domain name, a machine identification such as a serial number, and/or other numeric, textual, or other tag, label, address, or identifier. In embodiments, the alias can be registered in a lookup table, for instance embedded in provisioning profile 314 or otherwise. In aspects, the alias information can be stored in association with or pointing to an address or other identifier to locate or identify the target machine(s) in or to SAN 340, managed network 304, or other network, connection, or resource. In aspects, multiple aliases can be associated together to specify a target machine or other entity using a plurality of identifiers. Other formats for the alias and related information can be used. In 410, provisioning platform 302 can log into one or more SAN switch 308 using the alias and/or other identification information at the sync stage or other initialization stage of the provisioning process for the selected machines in set of targets 306.

In 412, provisioning platform 302 can add the recipient target(s) to any necessary netgroups to add those machines, whether physical or virtual, to the network file system (NFS) and/or other directory structure and/or file system or file configuration used by SAN 340, one or more network 304, and/or set of targets 306. In 414, provisioning platform 302 can receive and/or access set of storage specifications 324 identifying storage resources in set of storage resources 310 available in or to SAN 340 to fulfill set of storage allocations 322. In 416, provisioning platform 302 and/or other logic or resources can access, format, and/or mount one or more storage device and/or storage pool for each target machine using set of storage specifications 324. In 418, provisioning platform and/or other logic or resources can update and/or store set of storage specifications 324 and/or set of storage allocations 322, as appropriate. For instance, set of storage specifications 324 can be updated to reflect a substitute or additional RAID server or installation available in SAN 340, and which will be used to supply SAID requirements set out in set of storage allocations 322. In 420, processing can repeat, return to a prior processing point, jump to a further processing point, or end.

The foregoing description is illustrative, and variations in configuration and implementation may occur to persons skilled in the art. For example, while embodiments have been described which operate with one provisioning platform 302 and one SAN switch, in embodiments, multiple provisioning servers and/or other provisioning platforms and/or multiple storage area network switches can be used. For further example, while embodiments have been described in which one set of targets 306 may be provisioned together, in embodiments, multiple sets or groups of targets, or entire networks, can be provisioned and/or managed at the same time or in conjunction with the same provisioning processes. Other resources described as singular or integrated can in embodiments be plural or distributed, and resources described as multiple or distributed can in embodiments be combined. The scope of the present teachings is accordingly intended to be limited only by the following claims. 

1. A method of generating a set of storage allocations in a provisioning process, comprising: receiving a set of storage allocations for at least one target machine in a managed network; assigning a set of alias information to the at least one target machine identifying the at least one target machine to a storage area network; and accessing the storage area network using the alias to provision the set of storage allocations to the at least one target machine in association with the provisioning process.
 2. The method of claim 1, wherein the set of storage allocations comprises at least one of an amount of storage, a storage device type, a storage availability rating, or a backup allocation for the at least one target machine.
 3. The method of claim 1, wherein the set of alias information comprises a world wide port number (WWPN) associated with the at least one target machine.
 4. The method of claim 1, wherein the set of alias information further comprises a Fiber Channel (FC) alias associated with the world wide port number.
 5. The method of claim 1, wherein the provisioning process comprises distributing at least one of operating system software or a set of application software to the at least one target machine based on a provisioning profile.
 6. The method of claim 1, wherein at least one of the storage area network or the managed network uses a network file system (NFS).
 7. The method of claim 6, further comprising adding the at least one target machine to a netgroup to register the at least one target to the network file system (NFS) file configuration.
 8. The method of claim 1, wherein the at least one target machine comprises a physical machine.
 9. The method of claim 1, wherein the at least one target machine comprises a virtual machine.
 10. A provisioning system, comprising: an interface to at least one target machine in a managed network; and a processor, communicating with the at least one target machine, the processor being configured to— receive a set of storage allocations for the at least one target machine, assign a set of alias information to the at least one target machine identifying the at least one target machine to a storage area network, and access the storage area network using the alias to provision the set of storage allocations to the at least one target machine in association with the provisioning process.
 11. The system of claim 10, wherein the set of storage allocations comprises at least one of an amount of storage, a storage device type, a storage availability rating, or a backup allocation for the at least one target machine.
 12. The system of claim 10, wherein the set of alias information comprises a world wide port number (WWPN) associated with the at least one target machine.
 13. The system of claim 10, wherein the set of alias information further comprises a Fiber Channel (FC) alias associated with the world wide port number.
 14. The system of claim 10, wherein the provisioning process comprises distributing at least one of operating system software or a set of application software to the at least one target machine based on a provisioning profile.
 15. The system of claim 10, wherein at least one of the storage area network or the managed network uses a network file system (NFS) file configuration.
 16. The system of claim 15, wherein the processor is further configured to add the at least one target machine to a netgroup to register the at least one target to the network file system (NFS).
 17. The system of claim 10, wherein the at least one target machine comprises a physical machine.
 18. The system of claim 10, wherein the at least one target machine comprises a virtual machine.
 19. A target machine configured via a managed network, comprising: a first interface to at least one provisioning platform; a second interface to at least one storage area network; and a processor, communicating with the at least one provisioning platform via the first interface and the at least one storage area network via the second interface, the processor being configured to— receive a set of storage allocations for the target machine, and access the storage area network using the alias to provide the set of storage allocations assigned to the at least one target machine.
 20. The target machine of claim 19, wherein the set of storage allocations is stored in a provisioning store associated with the at least one provisioning platform. 